Unloaded entities are sometimes still accessible with `/execute on origin`

Expected behaviour

When an entity unloads, it should stop being accessible by any means (@e calls, or “execute on origin”).

Observed behaviour

Sometimes (inconsistent), the entity can still be targeted for a minute or so, even though it’s fully unloaded and not accessible with regular @e calls.

How to reproduce

I haven’t found a consistent setup for it (there might not be one), but this is how I found it:

1. /summon item_display ~ ~ ~ {Passengers:[{id:"minecraft:armor_stand",UUID:[I;1,2,3,4]}]}

2. /summon area_effect_cloud ~ ~ ~ {Owner:[I;1,2,3,4]}

3. Now teleport the item display far away so it unloads.

When performing these steps, the item display and armor stand won’t show up in @e calls, but both are sometimes still accessible with “execute as @n[type=area_effect_cloud] on origin” and “execute as @n[type=area_effect_cloud] on origin on vehicle” respectively.