Memory leak behavior in core-js DOM collection polyfills across versions

Goal

Determine whether core-js DOM collection polyfills exhibit memory leak patterns that persist across versions, particularly when used in long-running browser applications.

Constraints

The investigation must focus on documented behavior rather than unverified reports. Memory leak patterns may differ between core-js 2.x and 3.x branches due to architectural changes in the library's module system and polyfill loading strategy. Browser-specific behavior variations complicate generalization of findings.

Unresolved Questions

Do the DOM collection polyfills in core-js 3.x maintain references to DOM elements in a way that prevents garbage collection under specific browser engine implementations?

How does the memory retention behavior compare between the modular ES module exports introduced in core-js 3.x and the bundled approach of 2.x when polyfilling collection prototypes?

Are there documented cases where core-js's feature detection mechanism fails to properly clean up temporary references during polyfill initialization or re-initialization cycles?