Ive recently started experimenting with flex4.7+remoting+blazeds4+glassfish4.
Ive just noticed, that when i use a session scoped ro from the flex side, even if i programatically invalidate the FlexSession ( FlexContext.getFlexSession().[timeout()|invalidate()] ) the next call from the client side will be handled by the exact same ro instance.
-when i check out the sessionId from the FlexSession, it changes after invalidation, but the ro instance stays the same
-when i close the browser(with the flex app), and reopen it, the next ro-call will handled by an another instance
isnt this behavior the application scope behavior?
shouldnt get after session invalidation the ro instance destroyed?