There is another flushing statement after that for other cases.
Memoizing the locales for not logged in members was not a good idea and I guess it was solved in 5.1
Kevin's problem could be browser specific, it need some extra tracing.
What is obvious from the above description is that the server couldn't replace the previously existing cookie in the browser (But it could write a new one when the cookie was removed).
