Juniper policy actions in general are a match then exit. You can override this by sayinv 'next term' or 'next policy' but I don't know what sort of performance penalty making it process like that has, I'd guess very little since it is all in hardware and 'next term' basically forces a continue/rematch is all.