Edit11: Actually I think it may be thrown off a bit by THREE.js automatically resizing the texture to be a power of two anyway... Gah. So many little troubles.
Ah right, that's something we've talked of working around by storing the image in a power-of-two at runtime. Maybe! Here's an issue to discuss it, if anyone has input, please share.