Our RPC and subscriptions objects use a proxy to support arbitrary JSON-RPC methods. Currently we don't special-case any properties, and everything is treated as defined to return the async send() function.

See #508 where this causes an issue with the special then, which makes JS interpret our proxy as a valid promise.

We should check if there are any other standard properties that might cause similar issues where our proxy gets interpreted as providing functionality that it does not.