More cleanup that needs to be done when an interface isremoved

[Ted Lemon]

> The function used to be a no-op.  I turned it into a function that
> destroyed any io object sent to it.  I found that the client was crapping
> out when "connection" (IIRC) objects were being destroyed.  I can take out
> my hack to weed out non-interface objects and see where it is crapping if
> you like.

Hm.   I think the object gets destroyed when the underlying object is
dereferenced, in omapi_object_dereference.   The destroy routine is a
no-op because there isn't anything to free up in the I/O object.   I
don't think the destroy routine is supposed to free the object itself
- omapi_object_dereference does that.

			       _MelloN_