I can confirm that as well. Just updated and it’s not throwing this anymore. YAY!
I’m also having this issue across the flexible content modules. In fact I’m having this across all the ACF fields in a post. It’s acting like a different header has been given on save.