Rick is right -- to use 3dmerge to perform an inter-brick average, you would have to specify each sub-brick as a separate dataset entry. For your purposes, 3dTstat is much simpler.
The profusion of AFNI programs with similar and overlapping capabilities produces this problem of choosing how to do certain tasks, and I'm not sure how to address this issue.