The Entities Memory Profiler displays duplicate component entries for archetypes when multiple worlds exist. The number of duplicates scales with the number of worlds - with 3 worlds, each component is shown 3 times.
Steps to Reproduce
1. Create multiple worlds (e.g., ServiceWorld, ServerWorld, ClientWorld)
2. Ensure they share common archetypes
3. Open the Profiler window and select the Entities Memory module
4. Inspect any archetype's component list
Expected
Each component in an archetype should be listed once, regardless of how many worlds share that archetype.
Actual
Components are duplicated N times where N is the number of worlds sharing the archetype. For example, an archetype with Entity + SystemInstance + Simulate shows 12 components instead of 4 when 3 worlds exist.
Root Cause
In EntitiesProfiler.StaticData.ResetSessionMetaData(), when the profiler re-enables, it iterates through all worlds and records ArchetypeComponentData for each world's archetypes. If multiple worlds share the same archetype (same StableHash), the component data is recorded multiple times. Unlike WorldData and ArchetypeData, the component data was not being deduplicated when consumed by the Editor's MemoryProfilerModule.