The ConnectionMultiplexerManager.closeClientSession called when the multiplexer closes a session, but it doesn’t call either the sessionManager.sessionUnavailable() nor sessionManager.removeSession() method to destroy the route to the session.
This leads to Memory leak.
Cheers
Szabka