Possible Memory Leak in Orchestra

[Steve Ronderos <st...@ni.com>]

Hello Orchestra Developers,

I was wondering if anyone has any information on a potential memory leak 
that I see in Orchestra 1.2.

It appears to me that conversationManagers in ConversationWiperThread.java 
gets new ConversationManager objects added to it but they are only removed 
through some serialization method (I don't fully understand the 
distributed serialization stuff since I have never used it).  I think that 
this leak is pretty small... on the order of 10s of bytes per 
ConversationManager, but for long lasting high traffic apps that could 
eventually become a problem.  Is there something that I have overlooked 
that ensures that these are cleaned up? Is this an accepted shortcoming of 
Orchestra?  Should I file a JIRA issue?

Thanks,

Steve Ronderos