Tail recursion optimisation gets rid of all tail calls in functions, not just those that might lead to loops - you cannot in general detect those calls that might be loops. This can put a lot of holes in your stack trace.
It's an optimisation. It can be turned off when debugging with stack traces. If you need stack traces in production code, you have too many partial functions.
But you can't ever turn it off if you rely on it for loops, which defeats the whole point.
You can turn it off, you just can't process large data sets, as you'd run out of stack space. But who wants to debug with large data sets?
People who are debugging behaviour with large data sets perhaps? :P
The runtime could allocate "stack frames" on the heap, for such cases.