Unexpected HTTP response code for @Consumes mismatch

I have an interface with a method annotated as accepting XML (with @Consumes("application/xml") and @POST) and a class that implements that interface; the @Path is not matched for @POST by any other method. When I call it and pass in content with that MIME type, it all works. When I pass in content of another MIME type, I get a 404 response; this is unexpected, as I'd expect a 406 (Not Acceptable) response that tells me to pass in XML (to be clear, this is an error case). Having to work around this by accepting all types and doing my own content type negotiation is unacceptable, especially since that decreases the utility of the generated WADL file significantly. Surely CXF should be doing this sort of work for me?