ECMP Static route with BFD Issue

Greetings.  I have a Juniper MX480 running

Model: mx480
Junos: 14.2R4.9

We have a pair of LoadBalancer VMs in an Openstack enviornment using Open-BFD.  They handle incoming traffic for other processing VMs.  BFD is configured on both ends with static routes. In a recent test setup one of the LBs was administratively locked but we still saw application traffic coming in on the externally facing interfaces.  during inspection we saw that the BFD session was in a down state on both the MX and the LB. Normally when either of the LBs goes down, the BFD session will go down and the next-hop peer will be removed from the route tables.  In this instance the MX is not removing the down peer from the route table and still trying to send packets to the disabled LB. 

Config

labadmin@RTRL012# show routing-options static route 172.18.155.160/29
next-hop [ 172.18.113.145 172.18.113.146 ];
bfd-liveness-detection {
    minimum-interval 167;
    minimum-receive-interval 167;
    multiplier 3;
    no-adaptation;
}

labadmin@RTRL012> show configuration routing-options forwarding-table
export load-balancing-policy;

labadmin@RTRL012> show configuration policy-options policy-statement load-balancing-policy
then {
    load-balance per-packet;
}

Operational:

labadmin@RTRL012> show bfd session
                                                  Detect   Transmit
Address                  State     Interface      Time     Interval  Multiplier

.....

172.18.113.145           Up        irb.305        0.501     0.167        3
172.18.113.146           Down      irb.305        0.501     2.000        3

BFD Session is down BUT the peer is not removed from the MX route table.

labadmin@RTRL012> show route 172.18.155.161

inet.0: 1038 destinations, 1041 routes (1038 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

172.18.155.160/29  *[Static/5] 2d 02:43:46
                      to 172.18.113.145 via irb.305
                    > to 172.18.113.146 via irb.305

Any ideas why the Static route peer will still be enabled even though the BFD peer is down?

Thanks