No, this kind of thing is not possible with Java servlets.
Why don't you just but that stuff in a map in the application scope. That is what it was made for.
If there aren't too many concurrent users this should work but it will scale poorly.
Yeah, that's what I'm ending up doing, although I do have scaling concerns.
Not a huge deal, I'm just used to ATG's component structure where the session and request scopes are handled by application scoped managers, and key'ed by a UID. So you can get a session scoped component from the session manager if you have the session id and the component path.
I'll work with the Map thing for now.