Sure - there's a ton of them.The real problem is that "basic access authentication" was developed in the mid 1990s and never included a method to indicate the server was done with the client certification. Gotta love the stateless choice for an interface that has a state. It's still a discussed problem for any system using basic access authentication. http - How to log out user from web site using BASIC authentication? - Stack Overflow and HTTP authentication logout via PHP - Stack Overflow, for example. The heart of the problem is HTTP/1.1: Security Considerations where it says "This is a significant defect that requires further extensions to HTTP." I would love to read this mess, but not that interested anymore http://www.ietf.org/rfc/rfc2617.txt
Near as I can tell this was developed when browsers were single page at a time, so only one session existed at a time and closing the browser when done with a session was no big deal. The UI concept is similar to a keyfob for your car: Push the button to unlock the car and the car stays unlocked until the battery is removed from the car. No button to re-lock the car. Not their best thought.
This has been a thorn (rather than a full blown problem) for Windchill admins for a long time. They need to switch easily between user IDs to ensure that all the settings are right, but until recently Windchill had no method in place to support it. From the above response 10.1 allows the substitution of forms based authentication which does support 'logout' much like this support website does.
The stackoverflow articles are quite interesting, particularly for the way different browser makers all don't cooperate on solving what ended up, by spec, as a client side problem.