No, it is impossible using standard container-managed EJB persistence.

Yes, but you should provide custom implementation of the connection pool

Yes, but database servers should be located on different machines
and each machine should have its own application server instance running.

Yes, if databases are absolutely identical

Yes, if database server supports replication

Yes, you should include connection information into deployment descriptor file