That would be pretty much expected then. The message is telling you that you are no longer logged in as the person you were when the page was loaded, and thus you should refresh to see the changes.
If that changes the user -- either to a guest or someone else -- then the behavior is totally expected. If it doesn't, then their may be a bug of some sort, though we'd really need to be able to reproduce it to do some analysis of things like headers to see if something isn't being submitted as expected. (Which would be a pretty big breaking change from a browser, TBH.) Otherwise, it may be indicative of some sort of server-side issue, perhaps where a cached result is being returned unexpectedly. (Certainly something we have seen before in other situations.)