Memory leak from moving blocks that are far from the player

Using pistons to move blocks that are far away from the player triggers a memory leak. Possibly the same issue as (MCPE-65970) which may not have been fully fixed.

Steps to reproduce

1. Load the attached test world. It is a void flat world set to simulation distance 6. It contains an array of sticky pistons that move slime and honey blocks up and down.

2. Open resource monitor, select the memory tab, and note the memory used by Minecraft.

3. Flip the lever at -17, -64, 15

4. Observe the moving blocks. (Note that the movement animations are smooth.)

5. Wait 20 minutes and check the memory used by Minecraft in resource monitor.

6. Stand on the glowstone block at -95, -50, 0 and watch the array. (Note that the moving block animations are choppy and the piston arms are not rendered because they are outside the render distance for block entities.)

7. Wait 20 more minutes and check the memory used by Minecraft in resource monitor.

8. Watch the memory used by Minecraft for few minutes.

Expected result

The memory used by Minecraft should be about the same in steps (5) and (7). In step (8) it should stay about the same.

Observed result

The memory used by Minecraft is much higher in step (7) than in step (5), and in step (8) it rises steadily. If you continue step (8) for a longer time, the game will become unresponsive, consume all available RAM, and eventually crash.