Different behavior of task service on EAP6 and EAP7

If you start a process with a human task and abort it, one of two things will happen with the task based on which container you use:

1. EAP 6: The task will be destroyed and cannot be retrieved anymore.
2. EAP 7: The task will be moved to Exited state and can still be retrieved if you use the right filter.

This can be reproduced using both remote REST API and Business Central UI. I am not completely sure which behavior is the correct one. I only assume it is the former one because it has always been like this. In any case it needs to be the same on both containers.