Router layer accumulation causes unbounded memory growth in long-running Express applications

Context

Express 4.x stores every registered route and middleware as a Layer object in an internal array. Each call to app.use(), app.get(), or router.use() creates a new Layer that retains its path regular expression and handler references indefinitely. The framework provides no public API to deregister or remove these layers.

Problem

Applications that dynamically register routes at runtime—such as plugin architectures, micro-frontend integrations, or feature-flag-driven routing—experience unbounded heap growth because layers are never released. The core team has deferred a solution to user-space, leaving the design decision unresolved: whether router layers should be weakly referenced, expose a deregistration method, or remain permanently allocated.

Constraints

• Creating new Router instances per request is discouraged; routers must be instantiated at startup and reused.
• No official mechanism exists to inspect or prune the internal layer array.
• WeakMap-based workarounds in user-space cannot clean up the router's own layer references.

What patterns have proven effective for bounding router layer growth in production systems? Does the Express roadmap include any intention to expose layer lifecycle management? Are there version-specific behaviors in 4.17+ that mitigate or exacerbate this accumulation?