Robert, yes it's AGOL WAB.
I've opened a case with ESRI support. I beleive it may have something to do with a service that has a large number of layers published to a 10.2.2 server and being consumed in AGOL WAB. This behavior does not appear in teh WAB Dev Edition.
I'll update as it progresses.