Balance createTexture with destroyTexture

Running the moving-square example on OS X was leaking hundreds of megs of memory per second! Appears a `destroyTexture` call managed to slip away into some dark night.