[Bug] Memory leak in freshly generated Ember 3.28.8 app

[ctjhoa]

🐞 Describe the Bug

With a newly generated app with only one newly generated component, Ember Container is leaked after test run.
If you keeps executing test runs your memory keeps getting bigger and bigger.

🔬 Minimal Reproduction

https://github.com/concordnow/ember-memory-leaks-test

😕 Actual Behavior

Heap memory keeps increasing and Ember Container is still retained in memory

🤔 Expected Behavior

From my understanding, Ember Container should be garbage collected and should not remain in heap memory after a test run.

🌍 Environment

• Ember: - 3.28.8
• Node.js/npm: - Node v17.3.1 / npm 8.5.0
• OS: - Linux
• Browser: - Chromium

➕ Additional Context

I've already discuss this issue on discord with @chriskrycho
https://discord.com/channels/480462759797063690/501388188762505216/954029886803169292

[chriskrycho]

Thank you for reporting this! I've tagged it and hopefully someone will have a chance to poke at it sometime soon!

[pichfl]

Difficult to say precisely, but we might be running into similar issues in our project.

[mountHouli]

Hi Ember folks!

I'm using Hashicorp Vault. It uses Ember. My security team has flagged this issue and I am required to address it.

Does this bug still exist in Ember? Does it exist in Ember 4.x.x? Does it exist in Ember 5.x.x?

Thanks!