There is no set defined deployment order for the VDBs. VDBs are considered as individual schemas with no dependencies with each other. It may be possible to implement ordering as you mention above, but we not considering any more changes in Teiid 7.x line.
In Teiid 8.0 this becomes little hard, as all the deployments are happening in parallel, but if you know the VDB all names and their dependency structure, then there is possibilty for enhancement to define that.
Is your Teiid instance in the same container as your ears? If that's the case (ideally though you would be using a local non-socket connection), there can be an issue in AS loading order that causes exceptions such as that. Generally Teiid loads VDBs after DataSources become active. If you have a DataSource to a local Teiid instance, the use of that source may attempt to create connections before Teiid is ready. The simple fix is to set the min pool size to 0 to disable any pool preloading. In some scenarios application logic may still attempt to use a connection prior to Teiid being ready - see https://issues.jboss.org/browse/TEIID-2059 and https://issues.jboss.org/browse/TEIID-2122 however those fixes are not in a 7.x general release.