Ah yes, true, I only used this function for orthographic (aka parallel) projection.
With perspective projection, it makes more sense to return a ray, not a point. With this ray, one can do all kinds of intersections.
One could use the Z-buffer to figure out the closest object, but reading from the z-buffer with the CPU is rather slow, and might be rather inaccurate, but for testing purposes, that might work fine.
I guess it all comes down to what kind of "picking" interface one wants. It certainly would be nice to have an Event in reactive-fieldtrip for picking objects :) Since most (if not all?) geometry in fieldtrip is procedural, picking could be made exact?