@delle, further thoughts...
This log segment is interesting:
2015-10-05 19:18:02.139 openLuup.server:: request completed (1239743 bytes, 1921 ms) tcp{client}: 0xbeda80
2015-10-05 19:18:03.911 openLuup.server:: /J_ALTUI_utils.js tcp{client}: 0xdb3228
2015-10-05 19:18:03.920 openLuup.server:: request completed (34233 bytes, 9 ms) tcp{client}: 0xdb3228
2015-10-05 19:18:04.015 openLuup.server:: /J_ALTUI_verabox.js tcp{client}: 0xbeda80
2015-10-05 19:18:04.062 openLuup.server:: request completed (98266 bytes, 51 ms) tcp{client}: 0xbeda80
2015-10-05 19:18:04.119 openLuup.server:: /J_ALTUI_multibox.js tcp{client}: 0xdb3228
2015-10-05 19:18:04.125 openLuup.server:: request completed (28606 bytes, 6 ms) tcp{client}: 0xdb3228
2015-10-05 19:18:04.180 openLuup.server:: /J_ALTUI_uimgr.js tcp{client}: 0xbeda80
2015-10-05 19:18:04.247 openLuup.server:: request completed (411450 bytes, 67 ms) tcp{client}: 0xbeda80
2015-10-05 19:18:05.002 openLuup.server:: /luvd/D_FUP_uuid%205f9ec1b3-ed59-1900-4530-00117FAFD00A.xml tcp{client}: 0xdb3228
...I'm keen to know what the previous line was, or at least the item which led to a 1.2Mbyte response. At the same time it's very encouraging to see that the long transfer length problem seems to have been solved by the chunked transfer mode in the latest server version.
More helpfully, perhaps, this item:
D_FUP_uuid%205f9ec1b3-ed59-1900-4530-00117FAFD00A.xml
is UDN syntax, so UPnP origin, but I have absolutely no idea what it refers to. Strictly speaking, Vera is capable of using UDN in place of device numbers, but I've never seen it happen, and anyway this is a placeholder for a device filename. openLuup does not do UPnP (so not then, perhaps, a very good name for it!) Do you actually have anything like that file on your original Vera? (perhaps not in /etc/cmh-ludl/ but in /etc/cmh/ or elsewhere?)