Short answer is, No. They said there haven't been changes in ERROR. But, in the NAS configuration, there's a 'number of restarts' that's preset to 3. The tech I'm working with hinted that whatever code reads this might be new.
Here's what I think is happening:
When C/AL hits an ERROR, it restarts the NAS. It seems that it always has. But there's new code around how many times the NAS will attempt a restart before it fatally shuts down. THIS seems to be new in R2. In 2013, it would continue to restart until the cows came home.
I played around with the restart count configuration, but couldn't get it to be 'infinite'. I tried, -1, 0, and 99999. None of which actually worked.
I think our solution to this problem is to move to our own error handling code. Something that resembles the examples that Roberto Stefanetti posted previously. The TryCatch examples are an event system. A quick prototype shows that this would work.
If I get anything else from Microsoft, I'll update this thread.