Not beans themselves, no. A bean is something that can (in theory) be a member of more than one collection, although obviously putting a bean in both the session and request collections is a little silly. What you can do, however, is set up a listener to the collection itself. For example, when the session is destroyed, a session listener is a clue that all the beans in the session are going out of scope, since the scope itself is being destroyed. Beans don't just evaporate, so that's usually sufficient unless you have code that's manually inserting/removing beans.
An IDE is no substitute for an Intelligent Developer.
Joined: Dec 02, 2010
Thanks Tim. Is this the class I should be messing with: