CPU load during HTTP response can get sockets stuck

Huh... this is interesting.

console.log('about to start ap');
console.log(E.getErrorFlags());
wifi.startAP('test', {
  password: 'mytestap123',
  authMode: 'wpa2',
}, function(err) {
  if (err) { throw err; }

  console.log('started ap');
  console.log(E.getErrorFlags());
  console.log('about to start http');
  http.createServer(handleHTTPRequest).lis­ten(80);
  console.log('started http');
  console.log(E.getErrorFlags());
});

about to start ap
[ ]
=undefined
started ap
[
"FIFO_FULL"
]
about to start http
started http
[ ]