I understand, thanks Mark. 
I just wanted to let you know that it still seems to happen post September 26. The affected scripts were all created and added to my project around November 20th.
I have no problems with a work-around as simple as checking a flag. Now that I know about it I’ll recognize it immediately if it happens again.
Thanks for your hard work.
This fix to avoid new instances of these issues has been deployed yesterday, so this is just some already existing instances of the problem. Once fixed it should not come back again.
@KPal is investigating a way to either automatically fix those, or at least notify the user the project has this issue with instructions on how to fix it.
dont want another ghost children situation