What memory management issue commonly occurs in single-page applications (SPAs)?
Single-page applications commonly suffer from event listener memory leaks: 1) As views or components are destroyed and recreated, event listeners often aren't properly removed, 2) These orphaned listeners maintain references to old view elements and components, 3) This prevents garbage collection of components that should be destroyed, 4) The problem compounds over time as users navigate through the application, 5) SPAs are particularly vulnerable because they don't benefit from the complete page refresh that would clean up all listeners, 6) Framework-specific issues like failing to unsubscribe from observables or stores contribute to this problem, 7) These leaks are often subtle and only become apparent after extended use, 8) Proper component lifecycle management with explicit cleanup is essential for SPA memory health.