Three.js: The Pitfall of Modifying Objects During traverse()

I encountered an issue when I tried to remove the scene's children using traverse() as shown below:

scene.traverse((child) => {
    if (child.isNew) {
        scene.remove(child); // Modifies the scene's children array
    }
});

running this code snippet, only one scene's child was removed. I ask deepseek what the issue was, and I summarize its reply as follows:
Object3D.traverse() is a dynamic process, so the length of the children array change dynamically. When a child is removed, the array length used by the iteration process will be decreased by one, causing the traversal iteration to go wrong.

the solution is to avoid modifying scene's children during traversal process:

const childrenToRemove = [];

// Collect children to remove
scene.traverse((child) => {
    if (child?.isNew) {
        childrenToRemove.push(child);
    }
});

// Remove collected children
for (const child of childrenToRemove) {
    scene.remove(child);
}

by the way, there is a note in Three.js official document: Note: Modifying the scene graph inside the callback is discouraged. honestly, I didn't fully understand what that meant until this issue occurred.