The obvious answer is ultimately, the Ravens decided that they needed the salary cap space more than Leach and it just didn't make sense for essentially a part-time player to take up $4.33 million in cap room. Still, the pending move does spur some questions, a couple of which I'll attempt to answer below.
Why make the move now?
The timing is a little curious. Certainly, it doesn't look great for the Ravens to jettison a pro like Leach, who did everything the organization asked, a little more than a month before training camp. It doesn't give Leach a whole lot of time to find a new employer with cap room and a definitive need. Obviously, the Ravens didn't hold onto him until this late in the offseason out of spite. They wanted to keep him and thought they'd be able to work something out. If they didn't, they would have made the move immediately after they drafted Harvard's Kyle Juszczyk in the fourth round in April. However, as they got closer to training camp, the Ravens' top decision makers ultimately put more value on salary cap space than Leach's skill set. It's also important to point out that the team has had several weeks now to evaluate Juszczyk. If they didn't think he could handle the role, they wouldn't have made the move.