Basically request scoped beans are staying around after a full page refresh or a navigation rule execution. The "Text Enty" demo in Comp. Showcase uses an request scoped bean, type some text into it to update the backing bean. Then do a hard refresh of the browser of change the theme, the values are still here. This seems to be new behavior.
  
By definition, our Request scoped beans should be getting reconstructed on full page refreshes or navigation redirects/forwards.

I also see the request scoped persisting after the browser sends a <dispose-views> request. The procedure of opening a new View, doing some work, then disposing of the view will create a new Request scoped bean for each view, and while the View object is disposed of, the request scoped bean no longer is. If these request scoped beans add themselves to an IntervalRenderer or some such thing, the cleanup code using the disposableBeans interface no longer works, resulting in a growing collection of Renderables. Until the session expires.