There are at least two ways of improving the situation regarding this bug:

• use a conversation scope (from, say, Seam)
• detect browser window closing at the server and clean out requests corresponding to closed windows

As a first step we should look at how to propagate window closing events to the server. If window closing cannot be reliably propagated over the network at the moment of window closing, we may want to accumulate viewNumbers of closed windows in a cookie to propagate the closing event on the next exchange. (This may also present complications, however, as the browser will allow the user to close many windows simultaneously, and it may be difficult to update the cookie coherently.)

Ultimately, viewNumbers with unretrieved updates should be garbage collected.

Detect when browser windows are closed and disposed included views. Also, invoke listener to give a chance to applications to free up resources (such as connection, threads...).

This bug has been marked as fixed in 1.6DR#4. Can you please provide more information on the fix? I believe the issue still exists with 1.6DR#5. Does it require any specific configuration?

look like this is still hapening in the portlet version, request scope beans acts like session scope beans