After working with Salesforce customer support (partner case 15485269), this issue which occurred in the Winter '17 release has been resolved in the Spring '17 release. I have tested on my own org where the issue occurred and verified their fix after it was upgraded to Spring '17.
