Using oneOf/anyOf without careful consideration can be a performance killer

[unguul]

As per https://github.com/justinrainbow/json-schema/issues/640, having multiple oneOf entries can severely impact performance, especially when validating nested data.

While this might be an implementation specific problem, it might be worth adding some sort of warning in the docs to make people aware of this caveat.