jql causes OOME and instance restarted, due requested array size exceeding VM limit

Using the jql argument:

sprint was not 'x'

will cause an instance to restart due to array size requested being outside of virtual memory limit.

Initially reported on a large instance, this has been reproduced on a smaller instance with minimal sprints.

'Was Not' is an unsupported operator for the field sprint. Can the 'was not' operator be included in the list of supported operators? Alternatively can OOME be prevented when this query is executed in error?