Hi,
that looks like a numeric accuracy problem of the calculations on the GPU...
And it seems to be system/GPU specific, I was able to reproduce on iOS but not on my Windows system.
Will look for improvements.
As 'workaround' for the moment you could use a non-GPU drawn polygon by adding renderer="css3d" to the <hotspot>.
Best regards,
Klaus