Also, if you are bursting from a shared slave to a master, make sure that the first byte (or two) of the first and last packet are set to the shared address, and be careful to set the address on the slave again right after finishing the burst, specially in case of burst failures (i.e., send a broadcast message with the address field set to the slave's address). Otherwise, you may end up unintentionally changing your address to the first (or two) bytes of the last transmitted burst packet.
If communication from the slaves to the master is supposed to be spontaneous (i.e., not polled), a shared channel may not be the best fit for your application. A standard non-shared channel may be sufficient if communication from slave to master is infrequent. The shared channel uses polling to avoid collisions for systems with frequent communication from slaves to master - without the polling, and communicating only on address 0, it is really no different than a standard non shared channel.
You can find more details on this on Section 5.6 of the ANT Protocol and Message Usage Document.