Would you mind sharing a simplified example code that shows the "weird" behaviour?
If the result set is correct in DEBUGGING mode but wrong otherwise, that looks like a problem with parallel execution. You could set the SEQUENTIAL EXECUTION flag in your procedure to verify that.
Besides that - optimisation performed or not - it would still be a wrong result and therefore a bug.
Not sure why the colleagues call it out as a "special weird behaviour"...