Remove ward_ptr from bindings

Problem occurs when a pointer has been marked invalid after the Gorilla
element has been destroyed, and then subsequently Gorilla returns
another new element with the same pointer value.  A ward_ptr will think
this new pointer is invalid if the previous ward_ptr has not yet been
garbage collected.
Note about importaince now of setting rects to nil

after destroying.