In a navigation-heavy SwiftUI app, how did @Binding backfire over time?

Using @Binding in SwiftUI navigation can cause memory issues over time. When a binding is passed to a pushed view, it can close over large parent objects, keeping them alive even after navigation. The solution is to pass lightweight values instead and call back to the base, which prevents unintended retention and reduces memory footprint.