the problem with balancing the load via DNS is the Time To Live for each DNS response. In most cases this is not a problem, because Internet Host TTL is usually 24 hours. But, if you have a user that logs in around noon (for example) and then stays online until noon the next day, the user's network interface (IP stack) will issue a new DNS request and then you may (or may not) end up at a different application server. Very hard to replicate this phenonemon until you really understand DNS mechanisms.
One workaround is of course to limit session time to 23 hours or so. You should check back with your hosting provider as they maintain the authoritative records and steer the TTL for your devices.
Re load balancing by way of a parameter at application startup cannot work, because the load balancing has to occur before the initial HTTP request arrives at the system. There must be one single point of first contact (HTTP session handshake) and that is either a load balancer or redirection is done by providing different IP Addresses to different users (this is the DNS load balancing mechanism).
And re the copyrighted materials... of course anyone would like it if xojo shared it but on the other hand, what incentive would someone have to pay for the XDC event??? I guess that the XDC fees contribute to Xojo's revenue and they rely on it.