Occasionally spatial#collideWith will return a collision result with the distance at infinity. I suspect this occurs because in BIHNode the "hits" check is done in local coordinate space then done a second time in world space and numerical precision leads to the two having different answers.

My proposal is to include a second world-space isFinite test before committing the collision

Discussed at https://hub.jmonkeyengine.org/t/picking-sometimes-returns-infinite-distances/47715/2