When using clustering, the sessions created in the slave xadisk instances depend upon the concurrency-control of the master xadisk instance. If the master xadisk instance is a remote one, a proxy named RemoteConcurrencyControl is handed over to the sessions for the same. As this proxy object encapsulate a communication channel, so a new proxy object (hence a new channel) is needed for every such session. But sessions do not disconnect from these remote proxy objects. This leads to accumulation of channels, conversation-context (and their hosted object contexts) etc. Hence memory "leaks".
Solution is to disconnect from remote-concurrency-control as a session is done (eg in cleanup).