No, for Mendix developers this is not possible. But, if you are right, then it is also not your problem to solve since garbage collection is the task of the MBS, Mendix Business Server, which is maintained by Mendix. Best thing to do therefore is creating an application in which you can reproduce this behaviour (or copy your current project, strip it from things not related to this problem) and create a support ticket.
Hi Luke,
I had seen a similar behaviour in one of the apps, and I verified it, although it was in a different version of Mendix. I don't recall if it was just browser back or closing the page and I'm not sure if you're closing the page or not though.
It seems that Mendix garbage collection also runs when you close pages (too many times). See their official documentation:
https://docs.mendix.com/refguide/transient-objects-garbage-collecting
You can dump the client state with CTRL+ALT+G as discussed here.
It sounds like your reasoning is also correct – see 3.1.1 and 3.1.2 here.
You can also enable a special setting to see which objects are removed when garbage collections occur.
dojoConfig = { data: { "logCleanupStatistics": true }, ...}
enable debug logs in browser console.
Example: [Client] Garbage collecting 7 of 7 System.HttpHeader: 6473924464401166, 6473924464401171, 6473924464401170, 6473924464401169, 6473924464401168, 6473924464401167 System.HttpMessage: 8444249301321588
https://www.mendix.com/blog/the-art-of-state-part-2-garbage-collection/