In case anybody else stumbles upon this, the issue proved to be caused by an apparent bug in VMWare Studio's handling of HTML entities in the EULA text as far as I can figure. My initial finding was that removing all of the text from a specific semi-colon and onwards resolved the problem, though there were previous semi-colons in the text not causing any problems.
Replacing all of the & characters in the EULA text though ultimately solved the problem, so my best guess is the semi-colon in question was the first one following an ampersand character somewhere earlier in the text (I didn't go back to check afterwards).