Steps to reproduce:
1. Create a new Unity project

2. In the Built Profiles window, switch to the Web Platform

3. In the Platform Settings tab, enable “Development Build”

4. Click on the “Build and Run” button

5. Open the build in Google Chrome

6. Open the Dev Tools (right click anywhere on the page with your mouse and select “Inspect”)

7. Navigate to the Memory tab

8. Select "Heap snapshot" and click on the record button once to take a snapshot

9. In the Unity Build, click on the “Unload” button

10. Repeat step 8
11. Compare the two snapshots 

Actual results: The second snapshot has the WebGL memory allocated with similar values to the first snapshot
Expected results: The second snapshot has the WebGL memory released

Reproducible with: 6000.0.62f1, 6000.2.13f1, 6000.3.0f1, 6000.4.0a2
Could not reproduce with: 6000.5.0a1 (due to the errors when trying to build)

Reproducible on: MacOS 26.0.1 (M4)
Not reproducible on: No other environments tested

Notes:
- The values that aren't releasing the memory: ArrayBuffer, JSArrayBufferData, Context
- A discussion regarding this issue: [https://discussions.unity.com/t/memory-not-freed-when-exiting-the-unity-instance/1691880]
- 
The issue reproduces on Google Chrome, Firefox, and Microsoft Edge
- The issue wasn't tested on Safari because its memory profiling tools are less detailed