Memory growth during navigation operations

### Description

After repeated navigation operations, memory usage steadily rises and doesn't get reclaimed in a timely manner. Unfortunately, this heavily impacts our application due to the complexity of our pages. After ~40-50 navigations around our application, the application crashes from insufficient memory.

### Steps to Reproduce

### Link to public reproduction project repository

https://github.com/cdahlstrand/NavigationMemoryGrowth

Steps:
1. Clone the repository
2. Deploy to an Android device/emulator
3. Run the included `adb-touch.ps1` script to automate navigation
4. Observe memory growth in the output

### Version with bug

9.0.111 SR11.1

### Is this a regression from previous behavior?

Not sure, did not test other versions

### Last version that worked well

Unknown/Other

### Affected platforms

Android

### Affected platform versions

Android 13 - API 33

### Did you find any workaround?

No

Start with the public reproduction project at https://github.com/cdahlstrand/NavigationMemoryGrowth, deploy it on Android 13/API 33, and run the included adb-touch.ps1 script. Profile memory across repeated navigation operations to identify what remains allocated; done means the reproduced growth is resolved and the application no longer crashes after roughly 40–50 navigations.

Written by the indexing model from the issue text.