Hi,
I can only assume that this is a false positive marked by FastMM, we haven't received other reports. The SetActiveScene call is a class procedure that clears a global variable FScene: IScene in the destroy sequence of the component. This call is necessary to avoid invalid pointer issues. I suggest to raise this question with the developers of FastMM or use the default FastMM version in Delphi, where this issue does not occur.