remove two array allocations per deepEqual call (critical path)

[ngokevin]

Description:

From the browser performance tab, deepEqual was a large memory allocator. After this patch, deepEqual no longer even registers on the memory tab.

utils.deepEqual is called on every single component update. Saves two arrays per component update. For things like look-controls which updates pos/rot every frame, saves a lot.

Changes proposed:

• Don't use Object.keys in utils.deepEqual, use the same two arrays.

[dmarcos]

Failing tests

[ngokevin]

Fixed, I moved the object pooling utility from the other PR since the deepEqual call can get recursive, there's an uncertain amount of arrays we'd need to create.