Exposing intersectRay "bug" when passing vec4 as cp

This took me a week to pinpoint, and made me loose clawfuls of hair along the way.

It does not "bug" with all triangles, just some of them. All of the buggy triangles I could find had one vertex on the z=0 plane, but I don't know if it's related. And even with them, it's not all rays that bug. This is why the values in the test are not simple ones.

I'm solving this by using `[]` instead of `vec4.create()` in my app for now.

Also, Jasmine runs fast, especially when I target specific specs, but I takes ruby a dozen seconds to compile the assets needed to run. Is this normal, or am I missing optimization tweaks ?