v4.3.0 | In memory Token saving with no clean up leading to High Heap utilization and thus crashing JVM

[Shishir53]

Is there any cleanup strategy mentioned for v4.x for in memory token saving strategy?

#Update
While debugging the test application, I have found that when I click on InvaidateSession page, it removes one token but as unprotected page "session.jsp" is loaded, two master tokens are generated. Which results in token size increasing by 2 rather than decreasing by 1.
I have attached two snapshots below for reference.

[Shishir53]

See bug reported to understand the issue : #350
My question is: why not stop csrfguard from generating extra tokens, i.e. via handlesession method of csrfguardfilter after a call to OnSessionDestroyed() and made via listener. It uses same session key to generate new token which is never used and in previous step same session key was used to remove the token.