I have noticed in code that Director will load the next screen before releasing the previous one. So for a moment, this can cause a fairly significant memory spike. Are there any flags to avoid this? Something that would cause the previous screen to release before the next one is loaded? Right now I avoid this by allow "new" to return its display group but then I put a 100 ms timer in the screen and load the screen after that.