when user logout, the sessionDestroyed event is dispatched and JAASConversationStateListener listener will clear the coressponding Conversation object in the registry.

In WCI (TC7ServletContainerContext class) we have logout code like this:

//This will change the sessionID
servletRequest.logout();
...
//This code dispatch sessionDistroyed event
webapp.invalidateSession();
...

The JAASConversationStateListener receive session destroyed event but with a difference sessionID. Then it can not remove the corresponding Conversation object in the ConversationRegitry service
this cause memory leak in the ConversationRegitry and IdentityRegistry service

Should we fix this in WCI ? I'm not sure about the solution, can someone help me on this ?