Yup, this is a regression with the peephole optimizer, it's fixed and will be in the next release. All of the array work I was doing caused this to show up. Unit test added to ensure it doesn't happen again too. :)
Thanks for the report, super helpful!