Reproduction Steps:
1. Open the attached "IN-121469_REPRO" project
2. Open "Assets/OutdoorsScene.unity"
3. Open the Task Manager
4. Open the "Assets/Repro_Stuff/Empty_VFX" graph
5. Wait for the "Compiling compute variants" bar at the bottom right to finish loading
6. Enable the "Camera_TT" and "Empty_VFX_Holder" GameObjects in the Hierarchy window
7. Observe the result in Task Manager, in the Processes tab

Actual result: Memory increases rapidly and continuously
Expected result: Memory remains stable

Reproducible with: 2023.3.0a7, 6000.0.63f1, 6000.2.15f1, 6000.3.0f1 (d1870ce95baf), 6000.4.0a5, 6000.5.0a2
Could not test with: 2023.3.0a6 (Doesn't have needed VFX features)

Reproducible on: Windows 10 (customer), Windows 11
Not reproducible on: No other environments tested

Notes:
- Memory leak stops if you use Profiler (if the Profiler target is set to Editor and working)
- Sometimes the issue disappears, and you need to reopen the project
- If you open the reproduction project on older Unity Editor versions (2023.3.0a6) and later switch to 6000.5.0a2, the issue will not reproduce
- The memory leak is observed with any Visual Effect Graph (even if it is not used in the scene). It does not reproduce in Visual Scripting or Shader Graph
- When the project uses more than ~20 GB of RAM, it takes a while for the project to completely shut down after closing it (memory usage keeps slowly falling until it no longer appears in Task Manager) and can take multiple minutes to close in the background
- A good indicator of whether the bug will reproduce is the "Compiling compute variants" bar appearing after opening the project in the new editor for the first time