Using /kill on one of the end crystals used to respawn the ender dragon no longer aborts the respawn sequence

When the player breaks the end crystal on the exit portal, the code checks to see if it is one of the exit portal crystals.

When modding the behavior of end crystals to drop themselves, I came across this bug.

Because we have a list of EntityReferences instead of actual Entities, the contains method will never evaluate to true. [See image 1]

The only reason that the vanilla implementation works is that

List<EndCrystal> respawnCrystals = this.respawnCrystals.stream().map((e) -> (EndCrystal)e.getEntity(this.level, EndCrystal.class)).filter(Objects::nonNull).toList();
                if (respawnCrystals.isEmpty()) {
                    this.abortRespawnSequence();
                    return;
                }

it checks if ALL end crystals are gone, which coincidentally happens to be what happens to exit portal end crystals chaining together when they explode.