Potential memory leaks identified by KSPCommunityFixes

[Gordon-Dry]

Latest version of KSPCommunityFixes reports on some potential memory leaks on scene changes. A quick look in the log after scene change to Flight Scene shows 5 potential locations in SystemHeat where a leak might exist:

[LOG 21:14:59.011] [KSPCF:MemoryLeaks] A destroyed SystemHeat:SystemHeatUI instance is owning a onVesselChange GameEvents callback. No action has been taken, but unless this mod is relying on this pattern, this is likely a memory leak.
[LOG 21:14:59.025] [KSPCF:MemoryLeaks] A destroyed SystemHeat:SystemHeatUI instance is owning a onGUIApplicationLauncherUnreadifying GameEvents callback. No action has been taken, but unless this mod is relying on this pattern, this is likely a memory leak.
[LOG 21:14:59.025] [KSPCF:MemoryLeaks] A destroyed SystemHeat:ReactorToolbar instance is owning a onGUIApplicationLauncherUnreadifying GameEvents callback. No action has been taken, but unless this mod is relying on this pattern, this is likely a memory leak.
[LOG 21:14:59.025] [KSPCF:MemoryLeaks] A destroyed SystemHeat:SystemHeatUI instance is owning a onGUIApplicationLauncherDestroyed GameEvents callback. No action has been taken, but unless this mod is relying on this pattern, this is likely a memory leak.
[LOG 21:14:59.025] [KSPCF:MemoryLeaks] A destroyed SystemHeat:ReactorToolbar instance is owning a onGUIApplicationLauncherDestroyed GameEvents callback. No action has been taken, but unless this mod is relying on this pattern, this is likely a memory leak.