WASM Heap size greatly increases when UI elements are present in a WebGL build

How to reproduce:
1. Open the attached “IN-96546” project
2. Open the “SampleScene” Scene
3. Make sure that the “UIDocument” GameObject in the Hierarchy window is enabled
4. Build and run a WebGL build
5. Open the diagnostics panel by clicking the diagnostics icon under the game canvas
6. Observe the “Used WASM Heap” value
7. Delete the “UIDocument” GameObject from the “SampleScene” Scene
8. Build and run a WebGL build
9. Open the diagnostics panel by clicking the diagnostics icon under the game canvas
10. Observe the “Used WASM Heap” value

Expected result: The “Used WASM Heap” value decreases by ~10-20 MB after the second build
Actual result: The “Used WASM Heap” value decreases by ~100-110 MB after the second build

Reproducible with: 2023.1.0a22, 6000.0.42f1, 6000.1.0b10, 6000.2.0a6
Not reproducible with: 2022.3.60f1, 2023.1.0a21

Reproducible on: Windows 11
Not reproducible on: No other environments tested