Observing multicast replication on both member of ESI interfaces.

admin@Leaf-A> show interfaces ae36.0 extensive | match EVPN

Protocol eth-switch, MTU: 9216, Generation: 223, Route table: 9, Mesh Group: __all_ces__, EVPN multi-homed status: Forwarding, EVPN multi-homed ESI Split Horizon Label: 0, Next-hop: 1822,

admin@Leaf-B> show interfaces ae36.0 extensive | match EVPN

Protocol eth-switch, MTU: 9216, Generation: 225, Route table: 9, Mesh Group: __all_ces__, EVPN multi-homed status: Blocking BUM Traffic to ESI, EVPN multi-homed ESI Split Horizon Label: 0,

This is expected behavior for multicast traffic that is not receiving from vtep/upstream/core interfaces as illustrated in the following

Here, LEAF-1 performs the actions below:

• Does not send the traffic back to Host-1 (ACCESS-SPLIT-HRZN)
• Ingress Replicates traffic to all remote PEs over VTEP (CORE-IMET-FWD)
• Does not send to LEAF-5 as no Type-3 for VLAN-101. (CORE-IMET-SKIP)
• Sends traffic to Host-2 since it is single-homed interface (SH-FWD)
• Sends to Host-3, though it is NDF and it is access traffic (SRC-LOCAL-BIAS)

https://www.juniper.net/documentation/en_US/day-one-books/topics/topic-map/evpn-intra-vlan-multicast-without-optimization.html