AssetManager: Dependent assets remain loaded after primary asset is unloaded
Problem Statement When an asset that references other assets is unloaded via AssetManager.unload(), the dependent assets continue to occupy GPU and RAM memory, even though their reference counts drop to zero. Constraints AssetManager uses a global reference counter but does not traverse the dependency graph on unload. The API is identical across desktop, And