Yes, this is deliberate at present because we publish the derived WSDL and validate the configuration at that point. As mentioned earlier in the week though, this is easy to work around by using a local copy of the WSDL and will give you the behaviour you require.
I am saying if this is deliberate, we should fix it because it is a design flaw. That is why I opened the support ticket.